refactor: simplify async timer logic #3028
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What is changing?
Simplifying the logic so that we can reason more easily about the async scheduler.
The previous code was relying on the
NaN
timeSinceLastWake
correctly falling through on first wake, this refactor makes it so we rely on a more straightforward booleancannotBeExpedited
instead.Updating tests to use synchronous assertions since sinon fake timers don't require async callbacks to execute.
Is there new documentation needed for these changes?
No
What is the motivation for this change?
Hopefully reduce chance of accidental bugs
Double check the following
npm run check:lint
script<type>(NODE-xxxx)<!>: <description>